Correct tolerations placement in deployment #1965
Merged
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@adambethuggin thank you for the contribution! Can you please sign the commit? |
adambethuggin
force-pushed
the
patch-1
branch
from
cd9d707 to
b879d26
Compare
Fix improper tolerations configuration in kubearmorOperator Deployment The tolerations setting was placed incorrectly in the Deployment spec. This update relocates it to the correct section, allowing for intended functionality when deploying the operator. Signed-off-by: Adam Tuckett <[email protected]>
adambethuggin
force-pushed
the
patch-1
branch
from
b879d26 to
59268be
Compare
|
@rootxrishabh Sorry about that. Should be fixed now. Thanks!! |
rootxrishabh
approved these changes
Feb 6, 2025
rksharma95
approved these changes
Feb 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix improper tolerations configuration in kubearmorOperator Deployment
The tolerations setting was placed incorrectly in the Deployment spec. This update relocates it to the correct section, allowing for intended functionality when deploying the operator.
Purpose of PR?:
Fixes #1966
Does this PR introduce a breaking change?
This does not introduce a breaking change
Checklist: